Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] feat: harden post type usage and establish relationships between listings and posts/pages #43

Merged
merged 33 commits into from
Apr 29, 2021

Conversation

dkoo
Copy link
Contributor

@dkoo dkoo commented Feb 25, 2021

All Submissions:

Changes proposed in this Pull Request:

This one is kind of big! Does a few things to lay the groundwork for establishing cross-data-type relationships:

  1. Restricts the use of Business Listing patterns to the Place listing post type. This establishes Places as the de facto business data type, and Marketplace listings as more one-off classifieds which can be "owned" by one or more Places.
  2. Creates shadow taxonomies for each listing post type. These taxonomies are automatically created, updated, or deleted when posts of the corresponding listing types are created, renamed, or unpublished, respectively.
  3. Shadow taxonomies can be assigned to various post types. This lets us create associations between posts of different types—for example, Places can be assigned to Marketplace listings and Events. Listings can also be associated with other listings of the same type, which should let us show "related listings" more easily. This closes Harden post type usage #33.
  4. Each shadow taxonomy can be assigned to specific listings of other types, and all can be assigned to pages and posts. Closes Direct associations with Posts and Pages #34.
  5. When viewing a post, page, or listing that's been assigned listing shadow terms, we can automatically show a blurb and link for those associated listings. I've implemented a test version of this using the existing .author-bio styles from the Newspack theme, but this might need more design consideration (cc @thomasguillot).
  6. Adds a couple of test block patterns for Marketplace listings (in the form of real estate listings). These are definitely placeholder patterns that I created mainly for testing purposes, so we'll want to revisit in another PR (cc @thomasguillot).
  7. Adds a custom "Price" block that I figured would be useful for Marketplace listings (e.g. classifieds and real estate listings). This block editor is a fairly simple number input that also lets you select from a list of WooCommerce currencies (if available—defaults to the site's default currency, and falls back to USD if WooCommerce is not available) and then formats the number shown on the front-end with the corresponding currency symbol and internationalization based on the editor's browser settings—so if you choose Pound Sterling and you as an admin have a browser set to en-GB, it should show the number 10000 as £10,000.00. If you choose Euro and your browser is set to fr-FR, it should show 10 000,00 EUR. I based the formatting on the admin's browser settings because I figured that the price should be shown in the format familiar to the person creating the listing and choosing the currency. This block is also synced to a single meta field for listing CPTs, which automatically inherits the value from first instance of a Price block. This should be useful for future search and filtering features.

How to test the changes in this Pull Request:

Testing shadow taxonomies

  1. After checking out this branch, edit a post or page—you should now see sidebar panels for each listing post type alongside categories and tags. Also confirm that terms are automatically created for pre-existing published listings (so editors who are already running listings won't need to go back and update or recreate those to get the new terms).

Screen Shot 2021-03-31 at 4 31 51 PM

  1. Edit listings of each type and confirm that you see sidebar panels for the listing post types designated as being assignable in class-newspack-listings-taxonomies.php. For example, you should be able to assign Events to other Events and Generic listings, Generic listings only to other Generic listings, Marketplace listings to Generic listings and other Marketplace listings, and Places to all listing types.
  2. Assign some listings to posts, pages, and other listings and view the front-end.
  3. You should see blurbs for each assigned listing at the bottom of the content (see below):

Note: I'm not sure the language ("Listed by", "Related listings") is quite right, but I'm also not sure what these headings should say. It seems particularly weird to show "Listed by" when some of the blurbs are of the same type (e.g., showing an Event blurb on another Event), but I'm also not sure what we should show in the case of related listings of the same type. The blurbs also visually clash with author bios and sponsor blurbs, if those are enabled. Open to suggestions.

For example, on a post or page:
Screen Shot 2021-03-31 at 4 31 34 PM

On another listing:
Screen Shot 2021-03-31 at 4 25 36 PM

Testing shadow taxonomy updating/deleting

  1. Publish a new listing of any type.
  2. Edit a post, page, or another listing that is able to receive that listing type as a shadow term.
  3. Confirm that the new listing is searchable/selectable as a term in the editor sidebar.
  4. Revert the listing to a draft.
  5. Refresh the editor for the post/page/other listing and confirm that the listing term is no longer selectable or searchable.
  6. Publish a new post of any type other than a listing and confirm that no new term is created under any of the listing shadow taxonomies.

Testing Price block

  1. Create or edit a Marketplace listing.
  2. Confirm that a new block called "Price" is now insertable through the Block Inserter. Conversely, confirm that the Price block is not available in any other post type.

Screen Shot 2021-03-31 at 6 48 48 PM

  1. Test the block functionality:
  • Enter numbers in the input field. Confirm that you can only enter numbers greater than or equal to 0.
  • Confirm that the Currency field defaults to the currency set for your site in WooCommerce settings (which is set during Newspack onboarding). If you want to go above and beyond, you can install Listings on a fresh site without WooCommerce and confirm that a.) the Currency field is hidden, and b.) formatted prices are only shown in US dollars.
  • Confirm that when unfocusing the input field, the number is automatically formatted with the selected currency and decimals (if "Show decimals" is off, then the number is rounded to the nearest integer, if on, then it's shown to the nearest hundredth). Confirm that the same is true on the front-end.
  • Choose various currencies and test the symbols and formatting in both the editor and front-end.
  1. Change your browser language to something that will result in different number formatting than your usual language. For example, my Firefox is usually set to en-US, so I set it to fr-FR and restarted the browser app.
  2. Edit the Marketplace listing with your Price block and confirm that the number shown is formatted according to your browser's language setting. For example, before setting my Firefox to fr-FR, the number 500000 in EUR is shown as €500,000.00. After changing to French, it's shown as 500 000,00 €.
  3. Update the post and view on the front-end, and confirm the same. Verify that the format shown on the front-end matches the formatting last saved, not the reader's browser language.

Other information:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your changes, as applicable?
  • Have you successfully ran tests with your changes locally?

@dkoo dkoo self-assigned this Feb 25, 2021
@dkoo dkoo added this to the Phase 2 milestone Feb 25, 2021
@dkoo dkoo added the enhancement New feature or request label Feb 25, 2021
@dkoo dkoo linked an issue Feb 25, 2021 that may be closed by this pull request
@dkoo dkoo changed the title feat: harden post type usage and establish parent/child relationship b/w Places and Marketplace/Events feat: harden post type usage and establish relationships between listings and posts/pages Mar 31, 2021
@dkoo dkoo linked an issue Mar 31, 2021 that may be closed by this pull request
@dkoo dkoo marked this pull request as ready for review April 1, 2021 01:11
Copy link
Member

@adekbadek adekbadek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The core functionality, as well as the new block, work well. There are some issues though - apart from the ones in separate comment:

  1. The list of the assignable listings should not contain the edited listing.
  2. In the taxonomy panel in the sidebar, after clicking "Add new ", the text above the input says: "New Category Name". I'd expect it to say "New ". After filling out this new listing name, confirming, and publishing, the listing is not created. I think the "Add new…" should rather link to editor creating a new listing.

includes/class-newspack-listings-taxonomies.php Outdated Show resolved Hide resolved
src/blocks/price/edit.js Outdated Show resolved Hide resolved
src/blocks/price/view.php Outdated Show resolved Hide resolved
src/blocks/price/edit.js Outdated Show resolved Hide resolved
includes/class-newspack-listings-taxonomies.php Outdated Show resolved Hide resolved
}

/**
* When a Place changes status, add/update the shadow term if the status is `publish`, otherwise delete it.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is only one of the four listing types handled here? After reverting a generic listing to draft, it was still available in the taxonomy sidebar on a post.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was an oversight (since I started off with just one post type for testing). Should be fixed in a6f0195.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if that worked, I've found this issue:

  1. Create a Place
  2. Assign it to a Marketplace
  3. Rename the place
  4. Edit the Marketplace - there is now an additional Place taxonomy item - both old and new name are listed are assignable taxonomy options

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, the comment still mentions "Place" ;)

@dkoo dkoo requested a review from adekbadek April 22, 2021 23:12
Copy link
Member

@adekbadek adekbadek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(commented in existing thread)

@adekbadek
Copy link
Member

Should we consider adding a test suite in a separate PR after this lands? Since we're not releasing Phase 2 features until all are complete, we'd have a chance to catch any errors with this PR again once the tests are implemented.

Since this is not merged to master, the tests can be added later, but I'd be wary of merging Phase 2 as a single huge PR. This would introduce a lot of potential of errors.

@dkoo
Copy link
Contributor Author

dkoo commented Apr 23, 2021

I'd be wary of merging Phase 2 as a single huge PR. This would introduce a lot of potential of errors.

Definitely something I've thought about, but the features outlined for a Phase 2 release don't make much sense to roll out individually. The approach we've taken in reviewing and merging smaller PRs against a clone of master (while minimizing updates to master in the meantime) should hopefully minimize the errors when we finally merge that branch.

@dkoo dkoo requested review from adekbadek and removed request for jeffersonrabb April 26, 2021 19:53
@dkoo
Copy link
Contributor Author

dkoo commented Apr 29, 2021

@thomasguillot Since your redesigned UI won't affect the back-end portion of this PR, and this isn't getting released until all phase 2 PRs are approved, I'm going to merge this and handle the new UI in a separate PR.

@dkoo dkoo merged commit c04cb80 into epic/phase-2 Apr 29, 2021
@dkoo dkoo deleted the feat/data-type-usage branch April 29, 2021 18:01
@matticbot
Copy link
Contributor

🎉 This PR is included in version 2.0.0-alpha.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

dkoo added a commit that referenced this pull request Jul 6, 2021
* chore: replace AutocompleteTokenfield with Newspack Components version (#40)

* feat: use post categories and tags for all listing post types (#39)

* feat: use post categories and tags for all listing post types

* fix: undo patterns post type changes (for another PR)

* chore: remove unneeded admin page highlighting filter

BREAKING CHANGE: This feature will deprecate existing custom taxonomies, so any existing terms for those taxonomies will be lost.

To fix, we can convert terms from the deprecated taxonomies to standard post categories/tags via a migration script.


Fixes #32.

* feat: better integration with Newspack Theme features

* feat: add settings for individual listing type URL slugs

Closes #41.

* fix: wp_insert_post filter name and theme_mod filter

* fix: newspack_blocks support slug

* feat: add revisions support for listings

* chore: update outdated docblock

* refactor: use material icons with Newspack color

* fix: warning about default meta value

* fix: util for checking post type on new posts

* chore: update label of "hide author" setting

* feat: flush permalinks automatically if updating slug option

* feat: update cpt icon and block icons

See #49

* fix: remove material packages

* fix: failing npm ci command

* [WIP] feat: harden post type usage and establish relationships between listings and posts/pages (#43)

* feat: make Business patterns applicable only to places

* feat: create shadow taxonomy for places

* feat: add ability to associate Places with regular posts and pages

* fix: remove default map markers from patterns

* feat: new Price block for Marketplace listings

Also create a proof-of-concept Marketplace listing pattern to test block implementation.

* feat: add meta field with data synced from Price block

* feat: second test pattern

* fix: incorrect conditional for updating shadow terms (whoops)

* feat: abstract shadow tax functions to make it easier to add more

* refactor: simplify setting formattedPrice attribute via useEffect

* chore: fix PHP warning about passing variables

* feat: shadow taxonomies for all CPTs; test automated related listings

* fix: avoid showing post on itself

* fix: incorrect var assignment

* fix: decode HTML entities before rendering currency options

* chore: fix function/class docs

* fix: formatting an empty string results in NaN

* fix: wrong post type being returned by util

* fix: handle all listing post types for shadow taxonomies

* fix: don't show the shadow taxonomy for the post being edited

* feat: add new post button for shadow taxonomies

* chore: instantiate var as empty array, just in case

* fix: updating of terms, and delete orphan terms

* fix: replace Material icon with WordPress icon

* feat: custom UI for parent/child listings instead of WP taxonomy UI

* chore: update function comment

* chore: remove commented-out code

* fix: posts/pages child search fields; only show child UI if published

* fix: logical errors in validation method 🤦

* chore: update function name and comments for clarity

* refactor: use AutocompleteWithSuggestions from newspack-components (#56)

* feat: CSV importer script (#51)

* feat: init CSV importer via CLI command

* refactor: move importer files to subdir

* feat: take field mappings from config file instead of hard-coding them

* feat: add (currently unused) image_ids meta field for future use

* feat: process meta fields and content into block patterns

* fix: mismatch between data types in term handling

* feat: support multiple post types for importing

* docs: add README and sample config

* fix: do not apply content filters to legacy content upon importing

* chore: description

* fix: check if default post type constant is a listing

* feat: update block template; handle social media links

* feat: importer edits for GDG

* feat: add a new global setting and post option to hide date (#57)

* fix: use value property of selection from AutocompleteWithSuggestions (#61)

* fix: use value property of selection from AutocompleteWithSuggestions

* fix: cast listing ID value as an integer

* fix: cast listing IDs as strings to avoid breaking existing listings

* feat: convert legacy custom terms to regular post terms (#67)

* test: init test suite (#60)

* test: init test suite

* chore: fix function comment

* chore: remove redundant lint-php NPM script

* feat: if no view.php, register blocks with default attributes

* fix: activation PHP warning (#70)

* feat: support Newspack Sponsors for listings (#65)

* feat: support Newspack Sponsors

* refactor: response object with author and sponsors

* fix: sponsors for queried listings

* feat: update price block to use placeholder and large font size (#71)

* fix: guard against nonexistent meta object (#66)

* feat: child and related listings UI (#58)

* feat: initial exploration of UI in a modal

* fix: filter out parent post from child listings response

* feat: child and related listings UI

* chore: clear messages when closing modals

* chore: hide shadow terms from menu

* chore: handle errors from fetching suggestions

* chore: more context-sensitive labels for child/parent UI

* chore: update empty message

* refactor: make parent/child UI components more self-contained, reusable

* chore: update newspack-components

* fix: parent/child listings UI bugs

* chore: rename "Child Listings" to "Related Content"

* fix: default listings to one-column-wide.php post template (#77)

* chore: gate legacy taxonomy term deletion behind an environment constant

* fix: memory leaks from legacy term utilities (#81)

* feat: gate custom tax migration behind env flag to avoid expensive ops

* feat: move legacy taxonomy migrator script to a CLI command

* chore: rename CLI command and use ::log instead of ::line

* refactor: move missing/orphan shadow term handling to WP CLI

Co-authored-by: Thomas Guillot <info@thomasguillot.com>
Co-authored-by: Thomas Guillot <thomasguillot@users.noreply.github.com>
matticbot pushed a commit that referenced this pull request Jul 6, 2021
# [2.0.0-alpha.3](v2.0.0-alpha.2...v2.0.0-alpha.3) (2021-07-06)

* v2 release (#85) ([748810d](748810d)), closes [#85](#85) [#40](#40) [#39](#39) [#32](#32) [#41](#41) [#49](#49) [#43](#43) [#56](#56) [#51](#51) [#57](#57) [#61](#61) [#67](#67) [#60](#60) [#70](#70) [#65](#65) [#71](#71) [#66](#66) [#58](#58) [#77](#77) [#81](#81)

### Bug Fixes

* errors and bugs related to WP 5.8 ([#83](#83)) ([90da6c5](90da6c5))

### BREAKING CHANGES

* This feature will deprecate existing custom taxonomies, so any existing terms for those taxonomies will be lost.

To fix, we can convert terms from the deprecated taxonomies to standard post categories/tags via a migration script.
matticbot pushed a commit that referenced this pull request Jul 6, 2021
# [2.0.0](v1.2.2...v2.0.0) (2021-07-06)

* v2 release (#85) ([748810d](748810d)), closes [#85](#85) [#40](#40) [#39](#39) [#32](#32) [#41](#41) [#49](#49) [#43](#43) [#56](#56) [#51](#51) [#57](#57) [#61](#61) [#67](#67) [#60](#60) [#70](#70) [#65](#65) [#71](#71) [#66](#66) [#58](#58) [#77](#77) [#81](#81)

### Bug Fixes

* errors and bugs related to WP 5.8 ([#83](#83)) ([90da6c5](90da6c5))

### BREAKING CHANGES

* This feature will deprecate existing custom taxonomies, so any existing terms for those taxonomies will be lost.

To fix, we can convert terms from the deprecated taxonomies to standard post categories/tags via a migration script.
dkoo added a commit that referenced this pull request Jul 19, 2021
* chore: replace AutocompleteTokenfield with Newspack Components version (#40)

* feat: use post categories and tags for all listing post types (#39)

* feat: use post categories and tags for all listing post types

* fix: undo patterns post type changes (for another PR)

* chore: remove unneeded admin page highlighting filter

BREAKING CHANGE: This feature will deprecate existing custom taxonomies, so any existing terms for those taxonomies will be lost.

To fix, we can convert terms from the deprecated taxonomies to standard post categories/tags via a migration script.


Fixes #32.

* feat: better integration with Newspack Theme features

* feat: add settings for individual listing type URL slugs

Closes #41.

* fix: wp_insert_post filter name and theme_mod filter

* fix: newspack_blocks support slug

* feat: add revisions support for listings

* chore: update outdated docblock

* refactor: use material icons with Newspack color

* fix: warning about default meta value

* fix: util for checking post type on new posts

* chore: update label of "hide author" setting

* feat: flush permalinks automatically if updating slug option

* feat: update cpt icon and block icons

See #49

* fix: remove material packages

* fix: failing npm ci command

* [WIP] feat: harden post type usage and establish relationships between listings and posts/pages (#43)

* feat: make Business patterns applicable only to places

* feat: create shadow taxonomy for places

* feat: add ability to associate Places with regular posts and pages

* fix: remove default map markers from patterns

* feat: new Price block for Marketplace listings

Also create a proof-of-concept Marketplace listing pattern to test block implementation.

* feat: add meta field with data synced from Price block

* feat: second test pattern

* fix: incorrect conditional for updating shadow terms (whoops)

* feat: abstract shadow tax functions to make it easier to add more

* refactor: simplify setting formattedPrice attribute via useEffect

* chore: fix PHP warning about passing variables

* feat: shadow taxonomies for all CPTs; test automated related listings

* fix: avoid showing post on itself

* fix: incorrect var assignment

* fix: decode HTML entities before rendering currency options

* chore: fix function/class docs

* fix: formatting an empty string results in NaN

* fix: wrong post type being returned by util

* fix: handle all listing post types for shadow taxonomies

* fix: don't show the shadow taxonomy for the post being edited

* feat: add new post button for shadow taxonomies

* chore: instantiate var as empty array, just in case

* fix: updating of terms, and delete orphan terms

* fix: replace Material icon with WordPress icon

* feat: custom UI for parent/child listings instead of WP taxonomy UI

* chore: update function comment

* chore: remove commented-out code

* fix: posts/pages child search fields; only show child UI if published

* fix: logical errors in validation method 🤦

* chore: update function name and comments for clarity

* refactor: use AutocompleteWithSuggestions from newspack-components (#56)

* feat: CSV importer script (#51)

* feat: init CSV importer via CLI command

* refactor: move importer files to subdir

* feat: take field mappings from config file instead of hard-coding them

* feat: add (currently unused) image_ids meta field for future use

* feat: process meta fields and content into block patterns

* fix: mismatch between data types in term handling

* feat: support multiple post types for importing

* docs: add README and sample config

* fix: do not apply content filters to legacy content upon importing

* chore: description

* fix: check if default post type constant is a listing

* feat: update block template; handle social media links

* feat: importer edits for GDG

* feat: add a new global setting and post option to hide date (#57)

* fix: use value property of selection from AutocompleteWithSuggestions (#61)

* fix: use value property of selection from AutocompleteWithSuggestions

* fix: cast listing ID value as an integer

* fix: cast listing IDs as strings to avoid breaking existing listings

* feat: convert legacy custom terms to regular post terms (#67)

* test: init test suite (#60)

* test: init test suite

* chore: fix function comment

* chore: remove redundant lint-php NPM script

* feat: if no view.php, register blocks with default attributes

* fix: activation PHP warning (#70)

* feat: support Newspack Sponsors for listings (#65)

* feat: support Newspack Sponsors

* refactor: response object with author and sponsors

* fix: sponsors for queried listings

* feat: update price block to use placeholder and large font size (#71)

* fix: guard against nonexistent meta object (#66)

* feat: child and related listings UI (#58)

* feat: initial exploration of UI in a modal

* fix: filter out parent post from child listings response

* feat: child and related listings UI

* chore: clear messages when closing modals

* chore: hide shadow terms from menu

* chore: handle errors from fetching suggestions

* chore: more context-sensitive labels for child/parent UI

* chore: update empty message

* refactor: make parent/child UI components more self-contained, reusable

* chore: update newspack-components

* fix: parent/child listings UI bugs

* chore: rename "Child Listings" to "Related Content"

* fix: default listings to one-column-wide.php post template (#77)

* chore: gate legacy taxonomy term deletion behind an environment constant

* fix: memory leaks from legacy term utilities (#81)

* feat: gate custom tax migration behind env flag to avoid expensive ops

* feat: move legacy taxonomy migrator script to a CLI command

* chore: rename CLI command and use ::log instead of ::line

* refactor: move missing/orphan shadow term handling to WP CLI

* feat: block patterns for real estate and classifieds

* fix: import pattern styles into editor SCSS

* fix: restore patterns after merge

* refactor: remove placeholder image URLs from patterns

Co-authored-by: Thomas Guillot <info@thomasguillot.com>
Co-authored-by: Thomas Guillot <thomasguillot@users.noreply.github.com>
matticbot pushed a commit that referenced this pull request Jul 19, 2021
# [3.0.0-alpha.1](v2.0.1...v3.0.0-alpha.1) (2021-07-19)

### Bug Fixes

* avoid meta sync update error ([#95](#95)) ([cab16aa](cab16aa))
* do not register post-specific sidebars in widgets page ([#93](#93)) ([7716775](7716775))

### Features

* bump max number of items per list from 20 to 50 ([#97](#97)) ([009deab](009deab))
* more block patterns (real estate, classified ads) ([#84](#84)) ([e76acc3](e76acc3)), closes [#40](#40) [#39](#39) [#32](#32) [#41](#41) [#49](#49) [#43](#43) [#56](#56) [#51](#51) [#57](#57) [#61](#61) [#67](#67) [#60](#60) [#70](#70) [#65](#65) [#71](#71) [#66](#66) [#58](#58) [#77](#77) [#81](#81)

### BREAKING CHANGES

* This feature will deprecate existing custom taxonomies, so any existing terms for those taxonomies will be lost.

To fix, we can convert terms from the deprecated taxonomies to standard post categories/tags via a migration script.
matticbot pushed a commit that referenced this pull request Jul 19, 2021
# [3.0.0-alpha.1](v2.0.1...v3.0.0-alpha.1) (2021-07-19)

### Bug Fixes

* avoid meta sync update error ([#95](#95)) ([cab16aa](cab16aa))
* do not register post-specific sidebars in widgets page ([#93](#93)) ([7716775](7716775))

### Features

* bump max number of items per list from 20 to 50 ([#97](#97)) ([009deab](009deab))
* more block patterns (real estate, classified ads) ([#84](#84)) ([a51f5af](a51f5af))
* more block patterns (real estate, classified ads) ([#84](#84)) ([e76acc3](e76acc3)), closes [#40](#40) [#39](#39) [#32](#32) [#41](#41) [#49](#49) [#43](#43) [#56](#56) [#51](#51) [#57](#57) [#61](#61) [#67](#67) [#60](#60) [#70](#70) [#65](#65) [#71](#71) [#66](#66) [#58](#58) [#77](#77) [#81](#81)

### BREAKING CHANGES

* This feature will deprecate existing custom taxonomies, so any existing terms for those taxonomies will be lost.

To fix, we can convert terms from the deprecated taxonomies to standard post categories/tags via a migration script.
matticbot pushed a commit that referenced this pull request Jul 19, 2021
# 1.0.0-alpha.1 (2021-07-19)

### Bug Fixes

* avoid meta sync update error ([#95](#95)) ([cab16aa](cab16aa))
* do not register post-specific sidebars in widgets page ([#93](#93)) ([7716775](7716775))
* editor errors with reusable blocks ([#89](#89)) ([fdc46d3](fdc46d3))
* errors and bugs related to WP 5.8 ([#83](#83)) ([90da6c5](90da6c5))
* force alpha rebuild ([acc2075](acc2075))
* minor bug fixes ([#21](#21)) ([5f90bc7](5f90bc7))
* missing condition for block appender in list container ([#74](#74)) ([2c49896](2c49896))
* syncing attributes from curated list block to inner blocks ([#64](#64)) ([cdbc0bb](cdbc0bb))
* use synced attributes for ListContainer directly ([#73](#73)) ([f8641a7](f8641a7))

### Features

* add block patterns ([#23](#23)) ([a273a40](a273a40))
* bump max number of items per list from 20 to 50 ([#97](#97)) ([009deab](009deab))
* initial post type and block setup ([#1](#1)) ([47dc0c1](47dc0c1))
* listing taxonomies and query mode ([#6](#6)) ([528e1e5](528e1e5))
* more block patterns (real estate, classified ads) ([#84](#84)) ([a51f5af](a51f5af))
* new Curated List block, block pattern, and map functionality ([#3](#3)) ([9be6e7e](9be6e7e))
* remove borders and padding in editor to match front-end styles ([#14](#14)) ([6c47a17](6c47a17))

* v2 release (#85) ([748810d](748810d)), closes [#85](#85) [#40](#40) [#39](#39) [#32](#32) [#41](#41) [#49](#49) [#43](#43) [#56](#56) [#51](#51) [#57](#57) [#61](#61) [#67](#67) [#60](#60) [#70](#70) [#65](#65) [#71](#71) [#66](#66) [#58](#58) [#77](#77) [#81](#81)

### BREAKING CHANGES

* This feature will deprecate existing custom taxonomies, so any existing terms for those taxonomies will be lost.

To fix, we can convert terms from the deprecated taxonomies to standard post categories/tags via a migration script.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Direct associations with Posts and Pages Harden post type usage
3 participants